Messaging system with archived data display

ABSTRACT

Systems and computer-implement methods of displaying archived data are provided for determining that it is an anniversary of the archived data, the archived data including a message transmitted from a first client device to a second client device; causing display, on the first client device, of a graphical indicium and an avatar of a user associated with the first client device, the graphical indicium indicating an anniversary associated with the message transmitted from the first client device to the second client device; causing, display on the first client device of a notification of the anniversary; and causing the display of the graphical indicium and notification of the anniversary to be removed after a predefined time.

PRIOIRTY CLAIM

This application is a continuation of U.S. patent application Ser. No.16/588,285, filed on Sep. 30, 2019, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

The present disclosure relates to messaging systems, and particularly,but not exclusively, to retrieving and displaying archived data in amessaging system.

BACKGROUND

Electronic communications, such as e-mail or text messages, images,video, multimedia, and the like, over networks, such as the Internet,enable the quick communication of data between client devices.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexample embodiments.

FIG. 2 is a diagrammatic representation of a messaging clientapplication, in accordance with some example embodiments.

FIG. 3 is a diagrammatic representation of a data structure asmaintained in a database, in accordance with some example embodiments.

FIG. 4 is a diagrammatic representation of a message, in accordance withsome example embodiments.

FIG. 5 is a flowchart for an access-limiting process, in accordance withsome example embodiments.

FIG. 6 is block diagram showing a software architecture within which thepresent disclosure may be implemented, in accordance with some exampleembodiments.

FIG. 7 is a diagrammatic representation of a machine, in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed, in accordance with some example embodiments.

FIG. 8 is a diagrammatic representation of a processing environment, inaccordance with some example embodiments.

FIG. 9 is a flowchart illustrating a method 900 in accordance with oneembodiment.

FIG. 10 is a flowchart illustrating a method 1000 in accordance with oneembodiment.

FIG. 11A and 11B illustrate a GUI output 1100A and 1100B in accordancewith one embodiment.

DETAILED DESCRIPTION

Example embodiments resurface archived data (e.g., media such as savedchat media) transmitted between mobile devices on an anniversary of thedate the archived data was archived and/or created. The archived datacan comprise ephemeral messages that were archived (e.g., saved tomemory) despite being ephemeral. Embodiments display a tile indicatingthe date of the archived media (e.g., the exact date (e.g., Feb. 5,2017) or relative date (e.g., 2 years ago today)). Clicking on the tilewill cause the display of the archived data. If there are multiplearchived data, tiles representative of same can be displayed in reversechronological order. Accordingly, the example embodiments enable agraphical user interface (GUI) that solves the technical problem ofreminding a user of the availability of archived data that may otherwisebe forgotten as conventional GUIs in messaging systems may not enablesearching archived data.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple instances of a client device102, each of which hosts a number of applications including a messagingclient application 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via a network 106(e.g., the Internet).

A messaging client application 104 is able to communicate and exchangedata with another messaging client application 104 and with themessaging server system 108 via the network 106. The data exchangedbetween messaging client application 104, and between a messaging clientapplication 104 and the messaging server system 108, includes functions(e.g., commands to invoke functions) as well as payload data (e.g.,text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, the location of certain functionalityeither within the messaging client application 104 or the messagingserver system 108 is a design choice. For example, it may be technicallypreferable to initially deploy certain technology and functionalitywithin the messaging server system 108, but to later migrate thistechnology and functionality to the messaging client application 104where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include, message content, client device information,geolocation information, media annotation and overlays, message contentpersistence conditions, social network information, and live eventinformation, as examples. Data exchanges within the messaging system 100are invoked and controlled through functions available via userinterfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

The Application Program Interface (API) server 110 receives andtransmits message data (e.g., commands and message payloads) between theclient device 102 and the application server 112. Specifically, theApplication Program Interface (API) server 110 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client application 104 in order to invoke functionalityof the application server 112. The Application Program Interface (API)server 110 exposes various functions supported by the application server112, including account registration, login functionality, the sending ofmessages, via the application server 112, from a particular messagingclient application 104 to another messaging client application 104, thesending of media files (e.g., images or video) from a messaging clientapplication 104 to the messaging server application 114, and forpossible access by another messaging client application 104, the settingof a collection of media data (e.g., story), the retrieval of a list offriends of a user of a client device 102, the retrieval of suchcollections, the retrieval of messages and content, the adding anddeletion of friends to a social graph, the location of friends within asocial graph, and opening an application event (e.g., relating to themessaging client application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116 and a social network system 122. The messagingserver application 114 implements a number of message processingtechnologies and functions, particularly related to the aggregation andother processing of content (e.g., textual and multimedia content)included in messages received from multiple instances of the messagingclient application 104. As will be described in further detail, the textand media content from multiple sources may be aggregated intocollections of content (e.g., called stories or galleries). Thesecollections are then made available, by the messaging server application114, to the messaging client application 104. Other processor and memoryintensive processing of data may also be performed server-side by themessaging server application 114, in view of the hardware requirementsfor such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 (as shown in FIG.3 ) within the database 120. Examples of functions and servicessupported by the social network system 122 include the identification ofother users of the messaging system 100 with which a particular user hasrelationships or is “following”, and also the identification of otherentities and interests of a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., a story), selectively display and enableaccess to messages and associated content via the messaging clientapplication 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image video and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text and audio) may be organized into an “eventgallery” or an “event story.” Such a collection may be made availablefor a specified time period, such as the duration of an event to whichthe content relates. For example, content relating to a music concertmay be made available as a “story” for the duration of that musicconcert. The collection management system 204 may also be responsiblefor publishing an icon that provides notification of the existence of aparticular collection to the user interface of the messaging clientapplication 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion ofuser-generated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay or supplementation (e.g., an imagefilter) to the messaging client application 104 based on a geolocationof the client device 102. In another example, the annotation system 206operatively supplies a media overlay to the messaging client application104 based on other information, such as social network information ofthe user of the client device 102. A media overlay may include audio andvisual content and visual effects. Examples of audio and visual contentinclude pictures, texts, logos, animations, and sound effects. Anexample of a visual effect includes color overlaying. The audio andvisual content or the visual effects can be applied to a media contentitem (e.g., a photo) at the client device 102. For example, the mediaoverlay may include text that can be overlaid on top of a photographtaken by the client device 102. In another example, the media overlayincludes an identification of a location overlay (e.g., Venice beach), aname of a live event, or a name of a merchant overlay (e.g., BeachCoffee House). In another example, the annotation system 206 uses thegeolocation of the client device 102 to identify a media overlay thatincludes the name of a merchant at the geolocation of the client device102. The media overlay may include other indicia associated with themerchant. The media overlays may be stored in the database 120 andaccessed through the database server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay should be offered to other users. Theannotation system 206 generates a media overlay that includes theuploaded content and associates the uploaded content with the selectedgeolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time.

FIG. 3 is a schematic diagram illustrating data structures 300 which maybe stored in the database 120 of the messaging server system 108,according to certain example embodiments. While the content of thedatabase 120 is shown to comprise a number of tables, it will beappreciated that the data could be stored in other types of datastructures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table314. The entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, etc. Regardless of type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of variestypes, including user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a GPS unit of the client device102. Another type of filer is a data filer, which may be selectivelypresented to a sending user by the messaging client application 104,based on other inputs or information gathered by the client device 102during the message creation process. Example of data filters includecurrent temperature at a specific location, a current speed at which asending user is traveling, battery life for a client device 102, or thecurrent time.

Other annotation data that may be stored within the image table 308 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 302). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client application 104 may include an icon that isuser-selectable to enable a sending user to add specific content to hisor her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story”,which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some in some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from a memory        component of a client device 102, and that is included in the        message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from a memory component of the client        device 102, and that is included in the message 400.    -   A message annotations 412: annotation data (e.g., filters,        stickers or other enhancements) that represents annotations to        be applied to message image payload 406, message video payload        408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 400 was generated and from which the message        400 was sent    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 308.Similarly, values within the message video payload 408 may point to datastored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message group 504) may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, an ephemeral message 502 is viewable by a receiving userfor up to a maximum of 10 seconds, depending on the amount of time thatthe sending user specifies using the message duration parameter 506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message group 504 (e.g., a collection of messages in apersonal story, or an event story). The ephemeral message group 504 hasan associated group duration parameter 508, a value of which determinesa time-duration for which the ephemeral message group 504 is presentedand accessible to users of the messaging system 100. The group durationparameter 508, for example, may be the duration of a music concert,where the ephemeral message group 504 is a collection of contentpertaining to that concert. Alternatively, a user (either the owninguser or a curator user) may specify the value for the group durationparameter 508 when performing the setup and creation of the ephemeralmessage group 504.

Additionally, each ephemeral message 502 within the ephemeral messagegroup 504 has an associated group participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message group504. Accordingly, a particular ephemeral message group 504 may “expire”and become inaccessible within the context of the ephemeral messagegroup 504, prior to the ephemeral message group 504 itself expiring interms of the group duration parameter 508. The group duration parameter508, group participation parameter 510, and message receiver identifier424 each provide input to a group timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message group 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message group 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the group timer 514 operationally controls the overalllifespan of an associated ephemeral message group 504, as well as anindividual ephemeral message 502 included in the ephemeral message group504. In one embodiment, each and every ephemeral message 502 within theephemeral message group 504 remains viewable and accessible for atime-period specified by the group duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of ephemeral message group 504, based on a group participationparameter 510. Note that a message duration parameter 506 may stilldetermine the duration of time for which a particular ephemeral message502 is displayed to a receiving user, even within the context of theephemeral message group 504. Accordingly, the message duration parameter506 determines the duration of time that a particular ephemeral message502 is displayed to a receiving user, regardless of whether thereceiving user is viewing that ephemeral message 502 inside or outsidethe context of an ephemeral message group 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message group 504based on a determination that it has exceeded an associated groupparticipation parameter 510. For example, when a sending user hasestablished a group participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message group 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message group 504 either when the groupparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message group 504 has expired, or when theephemeral message group 504 itself has expired in terms of the groupduration parameter 508.

In certain use cases, a creator of a particular ephemeral message group504 may specify an indefinite group duration parameter 508. In thiscase, the expiration of the group participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message group504 will determine when the ephemeral message group 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage group 504, with a new group participation parameter 510,effectively extends the life of an ephemeral message group 504 to equalthe value of the group participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message group 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client application104) to cause an indicium (e.g., an icon) associated with the relevantephemeral message group 504 to no longer be displayed within a userinterface of the messaging client application 104. Similarly, when theephemeral timer system 202 determines that the message durationparameter 506 for a particular ephemeral message 502 has expired, theephemeral timer system 202 causes the messaging client application 104to no longer display an indicium (e.g., an icon or textualidentification) associated with the ephemeral message 502.

FIG. 6 is a block diagram 600 illustrating a software architecture 604,which can be installed on any one or more of the devices describedherein. The software architecture 604 is supported by hardware such as amachine 602 that includes processors 620, memory 626, and I/O components638. In this example, the software architecture 604 can beconceptualized as a stack of layers, where each layer provides aparticular functionality. The software architecture 604 includes layerssuch as an operating system 612, libraries 610, frameworks 608, andapplications 606. Operationally, the applications 606 invoke API calls650 through the software stack and receive messages 652 in response tothe API calls 650.

The operating system 612 manages hardware resources and provides commonservices. The operating system 612 includes, for example, a kernel 614,services 616, and drivers 622. The kernel 614 acts as an abstractionlayer between the hardware and the other software layers. For example,the kernel 614 provides memory management, processor management (e.g.,scheduling), component management, networking, and security settings,among other functionality. The services 616 can provide other commonservices for the other software layers. The drivers 622 are responsiblefor controlling or interfacing with the underlying hardware. Forinstance, the drivers 622 can include display drivers, camera drivers,BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers,serial communication drivers (e.g., Universal Serial Bus (USB) drivers),WI-FI® drivers, audio drivers, power management drivers, and so forth.

The libraries 610 provide a low-level common infrastructure used by theapplications 606. The libraries 610 can include system libraries 618(e.g., C standard library) that provide functions such as memoryallocation functions, string manipulation functions, mathematicfunctions, and the like. In addition, the libraries 610 can include APIlibraries 624 such as media libraries (e.g., libraries to supportpresentation and manipulation of various media formats such as MovingPicture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC),Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC),Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group(JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries(e.g., an OpenGL framework used to render in two dimensions (2D) andthree dimensions (3D) in a graphic content on a display), databaselibraries (e.g., SQLite to provide various relational databasefunctions), web libraries (e.g., WebKit to provide web browsingfunctionality), and the like. The libraries 610 can also include a widevariety of other libraries 628 to provide many other APIs to theapplications 606.

The frameworks 608 provide a high-level common infrastructure that isused by the applications 606. For example, the frameworks 608 providevarious graphical user interface (GUI) functions, high-level resourcemanagement, and high-level location services. The frameworks 608 canprovide a broad spectrum of other APIs that can be used by theapplications 606, some of which may be specific to a particularoperating system or platform.

In an example embodiment, the applications 606 may include a homeapplication 636, a contacts application 630, a browser application 632,a book reader application 634, a location application 642, a mediaapplication 644, a messaging application 646, a game application 648,and a broad assortment of other applications such as third-partyapplications 640. The applications 606 are programs that executefunctions defined in the programs. Various programming languages can beemployed to create one or more of the applications 606, structured in avariety of manners, such as object-oriented programming languages (e.g.,Objective-C, Java, or C++) or procedural programming languages (e.g., Cor assembly language). In a specific example, the third-partyapplications 640 (e.g., applications developed using the ANDROID™ orIOS™ software development kit (SDK) by an entity other than the vendorof the particular platform) may be mobile software running on a mobileoperating system such as IOS™, ANDROID™, WINDOWS® Phone, or anothermobile operating system. In this example, the third-party applications640 can invoke the API calls 650 provided by the operating system 612 tofacilitate functionality described herein.

FIG. 7 is a diagrammatic representation of a machine 700 within whichinstructions 708 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 700 to performany one or more of the methodologies discussed herein may be executed.For example, the instructions 708 may cause the machine 700 to executeany one or more of the methods described herein. The instructions 708transform the general, non-programmed machine 700 into a particularmachine 700 programmed to carry out the described and illustratedfunctions in the manner described. The machine 700 may operate as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 700 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 700 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), aPDA, an entertainment media system, a cellular telephone, a smart phone,a mobile device, a wearable device (e.g., a smart watch), a smart homedevice (e.g., a smart appliance), other smart devices, a web appliance,a network router, a network switch, a network bridge, or any machinecapable of executing the instructions 708, sequentially or otherwise,that specify actions to be taken by the machine 700. Further, while onlya single machine 700 is illustrated, the term “machine” shall also betaken to include a collection of machines that individually or jointlyexecute the instructions 708 to perform any one or more of themethodologies discussed herein.

The machine 700 may include processors 702, memory 704, and I/Ocomponents 742, which may be configured to communicate with each othervia a bus 744. In an example embodiment, the processors 702 (e.g., aCentral Processing Unit (CPU), a Reduced Instruction Set Computing(RISC) processor, a Complex Instruction Set Computing (CISC) processor,a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), anASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, orany suitable combination thereof) may include, for example, a processor706 and a processor 710 that execute the instructions 708. The term“processor” is intended to include multi-core processors that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.7 shows multiple processors 702, the machine 700 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core processor), multiple processors with a single core,multiple processors with multiples cores, or any combination thereof.

The memory 704 includes a main memory 712, a static memory 714, and astorage unit 716, both accessible to the processors 702 via the bus 744.The main memory 704, the static memory 714, and storage unit 716 storethe instructions 708 embodying any one or more of the methodologies orfunctions described herein. The instructions 708 may also reside,completely or partially, within the main memory 712, within the staticmemory 714, within machine-readable medium 718 within the storage unit716, within at least one of the processors 702 (e.g., within theprocessor's cache memory), or any suitable combination thereof, duringexecution thereof by the machine 700.

The I/O components 742 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 742 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones may include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 742 mayinclude many other components that are not shown in FIG. 7 . In variousexample embodiments, the I/O components 742 may include outputcomponents 728 and input components 730. The output components 728 mayinclude visual components (e.g., a display such as a plasma displaypanel (PDP), a light emitting diode (LED) display, a liquid crystaldisplay (LCD), a projector, or a cathode ray tube (CRT)), acousticcomponents (e.g., speakers), haptic components (e.g., a vibratory motor,resistance mechanisms), other signal generators, and so forth. The inputcomponents 730 may include alphanumeric input components (e.g., akeyboard, a touch screen configured to receive alphanumeric input, aphoto-optical keyboard, or other alphanumeric input components),point-based input components (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or another pointing instrument), tactileinput components (e.g., a physical button, a touch screen that provideslocation and/or force of touches or touch gestures, or other tactileinput components), audio input components (e.g., a microphone), and thelike.

In further example embodiments, the I/O components 742 may includebiometric components 732, motion components 734, environmentalcomponents 736, or position components 738, among a wide array of othercomponents. For example, the biometric components 732 include componentsto detect expressions (e.g., hand expressions, facial expressions, vocalexpressions, body gestures, or eye tracking), measure biosignals (e.g.,blood pressure, heart rate, body temperature, perspiration, or brainwaves), identify a person (e.g., voice identification, retinalidentification, facial identification, fingerprint identification, orelectroencephalogram-based identification), and the like. The motioncomponents 734 include acceleration sensor components (e.g.,accelerometer), gravitation sensor components, rotation sensorcomponents (e.g., gyroscope), and so forth. The environmental components736 include, for example, illumination sensor components (e.g.,photometer), temperature sensor components (e.g., one or morethermometers that detect ambient temperature), humidity sensorcomponents, pressure sensor components (e.g., barometer), acousticsensor components (e.g., one or more microphones that detect backgroundnoise), proximity sensor components (e.g., infrared sensors that detectnearby objects), gas sensors (e.g., gas detection sensors to detectionconcentrations of hazardous gases for safety or to measure pollutants inthe atmosphere), or other components that may provide indications,measurements, or signals corresponding to a surrounding physicalenvironment. The position components 738 include location sensorcomponents (e.g., a GPS receiver component), altitude sensor components(e.g., altimeters or barometers that detect air pressure from whichaltitude may be derived), orientation sensor components (e.g.,magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 742 further include communication components 740operable to couple the machine 700 to a network 720 or devices 722 via acoupling 724 and a coupling 726, respectively. For example, thecommunication components 740 may include a network interface componentor another suitable device to interface with the network 720. In furtherexamples, the communication components 740 may include wiredcommunication components, wireless communication components, cellularcommunication components, Near Field Communication (NFC) components,Bluetooth® components (e.g., Bluetooth® Low Energy), WiFi® components,and other communication components to provide communication via othermodalities. The devices 722 may be another machine or any of a widevariety of peripheral devices (e.g., a peripheral device coupled via aUSB).

Moreover, the communication components 740 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 740 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components740, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

The various memories (e.g., memory 704, main memory 712, static memory714, and/or memory of the processors 702) and/or storage unit 716 maystore one or more sets of instructions and data structures (e.g.,software) embodying or used by any one or more of the methodologies orfunctions described herein. These instructions (e.g., the instructions708), when executed by processors 702, cause various operations toimplement the disclosed embodiments.

The instructions 708 may be transmitted or received over the network720, using a transmission medium, via a network interface device (e.g.,a network interface component included in the communication components740) and using any one of a number of well-known transfer protocols(e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions708 may be transmitted or received using a transmission medium via thecoupling 726 (e.g., a peer-to-peer coupling) to the devices 722.

Turning now to FIG. 8 , there is shown a diagrammatic representation ofa processing environment 800, which includes a processor 802 (e.g., aGPU, CPU or combination thereof). In one example embodiment, theprocessing environment resides on a server system (e.g., messagingserver system 108).

The processor 802 is shown to be coupled to a power source 804, and toinclude (either permanently configured or temporarily instantiated)modules, namely a graphical user interface GUI renderer 806 that handlesbackend processing for rendering a GUI on a display of a device, amessage storage 808, and a flashback engine 810. The GUI renderer 806operationally generates an interface for displaying archived media, themessage storage 808 operationally stores the archived media, and theflashback engine 810 operationally determines when to retrieve archiveddata from the message storage 808 and display the retrieved archiveddata via the GUI renderer 806, as will be described further below.

FIG. 9 illustrates a method 900 in accordance with one embodiment.First, a client device, such as the client device 102 causes theflashback engine 810 on a server, such as the messaging server system108 comprising the processing environment 800, to archive (block 902)data, such as the ephemeral message 502, to the message storage 808. Forexample, a user may specify that specific data (e.g., a messagecomprising an image or video) that was sent and/or received by the usershould be archived. The client device will send a command to theflashback engine to archive the specified data. The flashback engine 810receives the command and archives the specified data.

In another example, data may be archived automatically after a specifiedperiod of time after the data was created or saved on the client device102. In the case of an ephemeral message, the data (e.g., ephemeralmessage) may be archived automatically after a timer indicates theephemeral message has expired.

In one example embodiment, the date the data was created and/or saved isalso saved with the archived data. In one example, the flashback engine810 archives the data to one or more data stores on a server system(e.g., messaging server system 108).

The archived data can include data transmitted from a first clientdevice to a second client device. For example, from a user's clientdevice to a second user's client device and might include a message,such as message 502.

Next, the flashback engine 810 determines (decision block 904) if it isan anniversary of the archived data by comparing the current date withan anniversary date. In one example, the anniversary is the date thedata was created or archived which is stored with the archived data. Inanother embodiment, the flashback engine 810 determines (decision block904) if a prespecified amount of time has passed since the archived datawas archived or created to determine if the current data is ananniversary date corresponding to when the archived data was archived orcreated.

Based on determining that the current date is an anniversary of thearchived data, the server system causes (block 906) display of agraphical indicium and an avatar of a user associated with the firstclient device, on a client device (e.g., via a GUI renderer 806). In oneexample, the server system causes a graphical indicium in the form of abadge on the avatar to be displayed on the client device. The badge mayindicate an anniversary. For example, a badge may include a yellowindicium in a top right corner of the avatar as shown in output 1116 ofFIG. 11A.

In one example, the client device is associated with a user who archivedthe data or for which the data was archived. For example, the clientdevice is associated with the user that created the data or sent thedata to the flashback engine to be archived. The graphical indicium(e.g., badge) may be displayed in a list of users of the messagingsystem 100 and/or list of conversations with other users singly or in agroup (or list of data exchanged with their client devices). Forexample, in the display 1102 in FIG. 11A an avatar of Emma in the list1114 is badged (1116), as will be discussed further below.

The flashback engine 810 also determines if (decision block 908) thecurrent date is a special occasion. A special occasion can be a list ofpredefined occasions with associated user data, such as birthdays,marriage anniversaries, and so forth, in contrast to the current datebeing an anniversary of the date the data was archived or created. Forexample, an anniversary might be 1 year since data was archived while aspecial occasion would be a birthdate. In one example, the flashbackengine 810 determines whether it is a special occasion by comparing thecurrent date with dates stored in the associated user data (e.g., theuser's birthdate, the user's wedding date, the user's first day ofwork). In another embodiment, a special occasion corresponding to theanniversary of the date the data was archived or created can bedetermined based on data in the archived data. For example, a birthdayor wedding anniversary greeting in the archived data would indicate itis a birthday or wedding anniversary.

If it is a special occasion, the client device causes (block 910) thedisplay on a GUI of the client device of a notification correlated to anoccasion corresponding to the anniversary of the archived data. In oneexample, the notification can appear on a tile or overlaying thearchived data. In another example, the notification can be a headingdisplayed on the GUI of the client device. For example, in the casewhere the special occasion is a birthday, the heading can include thefollowing string: [Participant first name of Display Name]'s BirthdayFlashback. In one example, the birthday may be applicable for more thanone user birthday (e.g., users of the first and second client devices).In this case, the users' heading can include, for example, the followingtitle string: “[First participant first name of Display Name] and[second participant first name of Display Name]'s Birthday Flashback”,and so on.

A user of the client device displaying the notification can click,touch, or otherwise interact with the notification to cause the displayof the archived data on the client device. For example, the clientdevice can detect when the user interacts with the tile and causedisplay of the archived data related to the occasion. In an embodiment,the archived data can be displayed inside the tile without the need foruser interaction to see the data. For example, the data may be a messagecomprising video and a thumbnail view of the video can be automaticallyplayed inside the tile. In one example, the server causes thenotification correlated to the occasion corresponding to the anniversaryof the archived data to be displayed on the client device bytransmitting the archived data from the server to the client device.

If the server determines that there is no special occasion, the servercauses display (block 912) on the client device associated with thearchived data of a tile on the anniversary with a notification (e.g.,heading) of the anniversary substantially similar to the displaying(block 910) above but instead of a special occasion notification, ageneric notification is provided. For example, “Our Flashback from[Date; e.g., “February 7”].” The causing to display operation (block 910or block 912) can also be performed by a client device that causedarchiving or did not causing archiving (e.g., a second device if a firstdevice caused the archiving).

A user of the client device displaying the notification can click,touch, or otherwise interact with the notification to cause the displayof the archived data on the client device. For example, the clientdevice can detect when the user interacts with a tile comprising thenotification and cause display of the archived data related to theoccasion. In an embodiment, the archived data can be displayed insidethe tile without the need for user interaction to see the data. Forexample, the data may be a message comprising video and a thumbnail viewof the video can be automatically played inside the tile. In oneexample, the server causes the notification correlated to the occasioncorresponding to the anniversary of the archived data to be displayed onthe client device by transmitting the archived data from the server tothe client device.

If (decision block 914) there is more archived data, the method 900returns to decision block 904 and displays the additional notificationsfor an anniversary or special occasion corresponding to archived data inreverse chronological order per block 910 and/or block 912. Selection ofa notification (e.g., by a user via a GUI on a client device) will causedisplay of the corresponding archived data as discussed above. In anembodiment, the archived data can be displayed inside a tile by, forexample, auto playing a thumbnail version of the archived data, as alsodescribed above.

If there is no more archived data at block 914, the GUI renderer 806causes (block 916) the graphical indicium and/or notification associatedwith the data to cease to display on the client device after apredetermined time (e.g., one full day). For example, the badge isremoved (block 918) after the predetermined time and/or after archiveddata is displayed (block 912). In one example, the predetermined time is24 hours starting at midnight of the client device in the earliest timezone. The method 900 then ends.

In an embodiment, the method 900 further comprises receiving a commandfrom the first or second device to cease displaying the archived data sothat the GUI renderer 806 ceases the display of a notification on thefirst and/or second mobile device.

In an embodiment, a user can send a command to re-save the archived data(e.g., a media collection) including the notification (e.g., related toan anniversary and/or special occasion?), and the flashback engine 810will create a duplicate copy of the media collection in the ‘Saved inChat’ section as archived above but further including the notification.

FIG. 10 is a flowchart illustrating a method 1000 in accordance with oneembodiment for archiving data on a computing device. The method 1000comprises receiving (block 1002), at a server (e.g., messaging serversystem 108) from a first client device, a command to send the archiveddata to a second client device. In one example, the server optionallysends (block 1004) a warning to the first client device related toprivacy of the archived data. For example, if the first client device issending the archived data to a device not associated with the archiveddata (e.g., that did not create or previously send the archived data),the server can send a privacy warning to the first client device.

The server system determines (decision block 1006) whether the firstdevice that sent the command to send the archived data to the secondclient device is the original creator of the archived data. If theserver system determines that the first device is the original creator(or associated with a user that was the original creator), the archiveddata is sent (block 1010) to the specified second client device. If theserver determines that the first device is not the original creator (ornot associated with a user that was the original creator), the serversends (block 1008) a notification to the a client device associated withthe original creator indicating that the first device (or a userassociated with a first device) has requested that archived data isbeing sent before sending the archived data to the second device (block1010). In one embodiment, the original creator can approve or notapprove sending of the archived data. In this embodiment, the serveronly sends the archived data if the server receives approval from theoriginal creator to send the archived data.

FIG. 11A illustrates example GUI output 1100 in accordance with oneembodiment. Output 1102 shows a list of contacts including individualsand groups. The Output 1102 includes a badge 1116 (as described abovewith respect to block 906) of an avatar of a user to indicate that it isan anniversary of archived data (created and/or archived date). Forexample, the avatar for user Emma is badged with a yellow badge. If auser selects the badged user, the GUI will display a tile 1118 showing adate of the archived data, as shown in output 1104. If the archived datahas not been viewed, a notification dot (e.g., in yellow) can be placedadjacent (e.g., to the right) of a header string. If viewed (e.g., afterviewing), the notification dot can be removed. If a user selects thetile 1118 in output 1104, the archived data is displayed, as shown inoutput 1106.

If a user wishes to send archived data to one or more other users, theuser can select one or more users from a list of users to which to sendthe archived data, as shown in output 1108, and output 1112 of FIG. 11B.In one example, the archived data can be sent with a pre-inputtedheading matching the notification (e.g., “Our Flashback from . . . ”.

Accordingly, embodiments enable the transmission and display of archiveddata on anniversary dates thereby improving access to the archived data.

“Carrier Signal” refers to any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device.

“Client Device” refers to any machine that interfaces to acommunications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network.

“Communication Network” refers to one or more portions of a network thatmay be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, a network or a portion of a network may include awireless or cellular network and the coupling may be a Code DivisionMultiple Access (CDMA) connection, a Global System for Mobilecommunications (GSM) connection, or other types of cellular or wirelesscoupling. In this example, the coupling may implement any of a varietyof types of data transfer technology, such as Single Carrier RadioTransmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard-setting organizations, other long-range protocols, or otherdata transfer technology.

“Component” refers to a device, physical entity, or logic havingboundaries defined by function or subroutine calls, branch points, APIs,or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a field-programmable gate array (FPGA) or an applicationspecific integrated circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software), may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component”(or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors 1004 orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

“Computer-Readable Medium” refers to both machine-storage media andtransmission media. Thus, the terms include both storage devices/mediaand carrier waves/modulated data signals. The terms “machine-readablemedium,” “computer-readable medium” and “device-readable medium” meanthe same thing and may be used interchangeably in this disclosure.

“Ephemeral Message” refers to a message that is accessible for atime-limited duration. An ephemeral message may be a text, an image, avideo and the like. The access time for the ephemeral message may be setby the message sender. Alternatively, the access time may be a defaultsetting or a setting specified by the recipient. Regardless of thesetting technique, the message is transitory.

“Machine-Storage Medium” refers to a single or multiple storage devicesand/or media (e.g., a centralized or distributed database, and/orassociated caches and servers) that store executable instructions,routines and/or data. The term shall accordingly be taken to include,but not be limited to, solid-state memories, and optical and magneticmedia, including memory internal or external to processors. Specificexamples of machine-storage media, computer-storage media and/ordevice-storage media include non-volatile memory, including by way ofexample semiconductor memory devices, e.g., erasable programmableread-only memory (EPROM), electrically erasable programmable read-onlymemory (EEPROM), FPGA, and flash memory devices; magnetic disks such asinternal hard disks and removable disks; magneto-optical disks; andCD-ROM and DVD-ROM disks The terms “machine-storage medium,”“device-storage medium,” “computer-storage medium” mean the same thingand may be used interchangeably in this disclosure. The terms“machine-storage media,” “computer-storage media,” and “device-storagemedia” specifically exclude carrier waves, modulated data signals, andother such media, at least some of which are covered under the term“signal medium.”

“Processor” refers to any circuit or virtual circuit (a physical circuitemulated by logic executing on an actual processor) that manipulatesdata values according to control signals (e.g., “commands”, “op codes”,“machine code”, etc.) and which produces corresponding output signalsthat are applied to operate a machine. A processor may, for example, bea Central Processing Unit (CPU), a Reduced Instruction Set Computing(RISC) processor, a Complex Instruction Set Computing (CISC) processor,a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), anApplication Specific Integrated Circuit (ASIC), a Radio-FrequencyIntegrated Circuit (RFIC) or any combination thereof. A processor mayfurther be a multi-core processor having two or more independentprocessors (sometimes referred to as “cores”) that may executeinstructions contemporaneously.

“Signal Medium” refers to any intangible medium that is capable ofstoring, encoding, or carrying the instructions for execution by amachine and includes digital or analog communications signals or otherintangible media to facilitate communication of software or data. Theterm “signal medium” shall be taken to include any form of a modulateddata signal, carrier wave, and so forth. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a matter as to encode information in the signal. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure.

The following examples describe various embodiments of methods,machine-readable media, and systems (e.g., machines, devices, or otherapparatus) discussed herein.

1. A computer-implement method of displaying archived data, comprising:determining, by a server system, that it is an anniversary of thearchived data, the archived data including a message transmitted from afirst client device to a second client device; causing, by the serversystem, display, on the first client device, of a graphical indicium andan avatar of a user associated with the first client device, thegraphical indicium indicating an anniversary associated with the messagetransmitted from the first client device to the second client device;

causing, by the server system, display on the first client device of anotification of the anniversary; and

causing, by the server, the display of the graphical indicium andnotification of the anniversary to be removed after a predefined time.

2. The method of example 1, wherein the message is an ephemeral message.

3. The method of example 1, further comprising causing a headingcorrelated to an occasion corresponding to the anniversary of thearchived data to be displayed on the first client device.

4. The method of example 1, further comprising causing display, inreverse chronological order, of additional archived data on the firstclient device that archived the additional data.

5. The method of example 1, further comprising causing display of thearchived data on the second client device.

6. The method of example 1, further comprising:

receiving, at the server from the first or second client device, acommand to send the archived data to a third client device;

sending, by the server, to a creator of the archived data, anotification of the command to send; and

sending, by the server, the archived data to the third client deviceupon receiving approval to do so from the creator of the archived data.

7. A server system for transmitting mobile device battery data,comprising: one or more processors of a server;

a memory storing instruction that, when executed by the one or moreprocessors, cause the server to perform operations comprising:

determining, by the server system, that it is an anniversary of thearchived data, the archived data including a message transmitted from afirst client device to a second client device;

causing, by the server system, display, on the first client device, of agraphical indicium and an avatar of a user associated with the firstclient device, the graphical indicium indicating an anniversaryassociated with the message transmitted from the first client device tothe second client device;

causing, by the server system, display on the first client device of anotification of the anniversary; and

causing, by the server, the display of the graphical indicium andnotification of the anniversary to be removed after a predefined time.

8. The system of example 7, wherein the message is an ephemeral message.

9. The system of example 7, wherein the operations further comprisecausing a heading correlated to an occasion corresponding to theanniversary of the archived data to be displayed on the first clientdevice.

10. The system of example 7, wherein the operations further comprisecausing display of the archived data on the second client device e.

11. The system of example 7, wherein the operations further comprisecausing display, in reverse chronological order, of additional archiveddata on the first client device that archived the additional data.

12. The system of example 7, wherein the operations further comprise:

receiving, at the server from the first or second client device, acommand to send the archived data to a third client device;

sending, by the server, to a creator of the archived data, anotification of the command to send; and

sending, by the server, the archived data to the third client deviceupon receiving approval to do so from the creator of the archived data.

13. A machine-readable storage device embodying instructions that, whenexecuted by a server system, cause the server to perform operationscomprising:

determining, by the server system, that it is an anniversary of thearchived data, the archived data including a message transmitted from afirst client device to a second client device;

causing, by the server system, display, on the first client device, of agraphical indicium and an avatar of a user associated with the firstclient device, the graphical indicium indicating an anniversaryassociated with the message transmitted from the first client device tothe second client device;

causing, by the server system, display on the first client device of anotification of the anniversary; and

causing, by the server, the display of the graphical indicium andnotification of the anniversary to be removed after a predefined time.

14. The machine-readable storage device of example 13, wherein themessage is an ephemeral message.

15. The machine-readable storage device of example 13, wherein theoperations further comprise causing a heading correlated to an occasioncorresponding to the anniversary of the archived data to be displayed onthe first client device.

16. The machine-readable storage device of example 13, wherein theoperations further comprise causing display of the archived data on thesecond client device.

17. The machine-readable storage device of example 13, wherein theoperations further comprise causing display, in reverse chronologicalorder, of additional archived data on the first client device thatarchived the additional data.

18. The machine-readable storage device of example 13, wherein theoperations further comprise:

receiving, at the server from the first or second client device, acommand to send the archived data to a third client device;

sending, by the server, to a creator of the archived data, anotification of the command to send; and

sending, by the server, the archived data to the third client deviceupon receiving approval to do so from the creator of the archived data.

19. The machine-readable storage device of example 13, wherein thecausing displaying displays a thumbnail view of video inside a tile.

20. The machine-readable storage device of example 13, wherein thegraphical indicium is a badge.

What is claimed is:
 1. A method comprising: relaying, from a firstclient device to a second client device by a server system, a messagegenerated by the first device; after the relaying, in response to arequest from the first client device, archiving, by the server system,user-selected data including the message; determining, by the serversystem, that a current corresponds to a criterion; and causing, by theserver system, display, on the first client device, of a list of userswith a graphical indicium and an avatar of a user from the listassociated with the second client device, the graphical indiciumindicating the criterion associated with the message transmitted fromthe first client device to the second client device.
 2. The method ofclaim 1, wherein the message is an ephemeral message.
 3. The method ofclaim 1, further comprising: causing a heading correlated to an occasioncorresponding to the criterion of the archived data to be displayed onthe first client device.
 4. The method of claim 1, further comprising:causing display, in reverse chronological order, of additional archiveddata on the first client device that archived the additional data. 5.The method of claim 1, further comprising: causing display of thearchived data on the second client device.
 6. The method of claim 1,further comprising: receiving, at the server from the first or secondclient device, a command to send the archived data to a third clientdevice; sending, by the server, to a creator of the archived data, anotification of the command to send; and sending, by the server, thearchived data to the third client device upon receiving approval to doso from the creator of the archived data.
 7. A server system fordisplaying archived data, comprising: one or more processors of aserver; a memory storing instruction that, when executed by the one ormore processors, cause the server system to perform operationscomprising: relaying, from a first client device to a second clientdevice by a server system, a message generated by the first device;after the relaying, in response to a request from the first clientdevice, archiving, by the server system, user-selected data includingthe message; determining, by the server system, that a currentcorresponds to a criterion; and causing, by the server system, display,on the first client device, of a list of users with a graphical indiciumand an avatar of a user from the list associated with the second clientdevice, the graphical indicium indicating the criterion associated withthe message transmitted from the first client device to the secondclient device.
 8. The system of claim 7, wherein the message is anephemeral message.
 9. The system of claim 7, wherein the operationsfurther comprise causing a heading correlated to an occasioncorresponding to the criterion of the archived data to be displayed onthe first client device.
 10. The system of claim 7, wherein theoperations further comprise causing display of the archived data on thesecond client device.
 11. The system of claim 7, wherein the operationsfurther comprise causing display, in reverse chronological order, ofadditional archived data on the first client device that archived theadditional data.
 12. The system of claim 7, wherein the operationsfurther comprise: receiving, from the first or second client device, acommand to send the archived data to a third client device; sending, toa creator of the archived data, a notification of the command to send;and sending the archived data to the third client device upon receivingapproval to do so from the creator of the archived data.
 13. Anon-transitory machine-readable storage device embodying instructionsthat, when executed by a server system, cause the server system toperform operations comprising: relaying, from a first client device to asecond client device by a server system, a message generated by thefirst device; after the relaying, in response to a request from thefirst client device, archiving, by the server system, user-selected dataincluding the message; determining, by the server system, that a currentcorresponds to a criterion; and causing, by the server system, display,on the first client device, of a list of users with a graphical indiciumand an avatar of a user from the list associated with the second clientdevice, the graphical indicium indicating the criterion associated withthe message transmitted from the first client device to the secondclient device.
 14. The machine-readable storage device of claim 13,wherein the message is an ephemeral message.
 15. The machine-readablestorage device of claim 13, wherein the operations further comprisecausing a heading correlated to an occasion corresponding to thecriterion of the archived data to be displayed on the first clientdevice.
 16. The machine-readable storage device of claim 13, wherein theoperations further comprise causing display of the archived data on thesecond client device.
 17. The machine-readable storage device of claim13, wherein the operations further comprise causing display, in reversechronological order, of additional archived data on the first clientdevice that archived the additional data.
 18. The machine-readablestorage device of claim 13, wherein the operations further comprise:receiving, from the first or second client device, a command to send thearchived data to a third client device; sending, to a creator of thearchived data, a notification of the command to send; and sending thearchived data to the third client device upon receiving approval to doso from the creator of the archived data.
 19. The machine-readablestorage device of claim 13, wherein the graphical indicium is a badge.20. The machine-readable storage device of claim 13, wherein the messageincludes video and the operations further comprise: causing, by theserver system, display on the first client device of a notification ofthe criterion; causing, by the server system, automatic display of thevideo on the first client device in a thumbnail view without a usercommand; and ceasing displaying the video on the first client device inresponse to a command from the second client device.